Add migration to fix SSL flag in DB for edge cases #456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new database migration to ensure that the SSL flag in the database correctly reflects the presence of valid Let's Encrypt certificates for existing sites. The migration checks for orphaned redirect configuration files, verifies SSL certificate issuers, and updates the database as needed, logging all actions for traceability.
Key changes in the migration:
SSL flag correction and certificate validation:
FixSslFlagForExistingLeCerts) that iterates over all sites, checks for the presence and validity of Let's Encrypt certificates, and updates thesite_sslflag in the database to'le'if a valid Let's Encrypt certificate is detected.